Skip to content

Conversation

@tarasmadan
Copy link
Collaborator

@tarasmadan tarasmadan commented Jun 4, 2025

The impact score is deducted from the title.
Moves #6071 forward.

@tarasmadan tarasmadan force-pushed the bug-impact-column branch 10 times, most recently from d9b86ff to e7160e6 Compare June 4, 2025 20:42
@tarasmadan tarasmadan marked this pull request as ready for review June 4, 2025 20:44
@FlorentRevest
Copy link
Collaborator

I love this... :)

FWIW, I've additionally been prioritizing bugs based on 1- whether they obviously don't need privileges (do reproducers trivially work in the setuid(nobody) instance ?) 2- do they use some sort of fault injection/hwpoison ? 3- do they use a corrupted file system (based on the fsck result) 4- whether they happen orders of magnitude more often than the rest (because it impacts syzbot's ability to find other bugs)

It may be hard to throw all of this into a score but I wanted to put it out there for discussion

@tarasmadan tarasmadan force-pushed the bug-impact-column branch 3 times, most recently from 34706b3 to 89fb83e Compare July 3, 2025 15:38
@tarasmadan tarasmadan force-pushed the bug-impact-column branch 5 times, most recently from e75eef4 to b116e48 Compare July 7, 2025 10:19
@tarasmadan tarasmadan force-pushed the bug-impact-column branch 2 times, most recently from b28bc1a to 01dbb6e Compare July 8, 2025 10:21
The impact score is deducted from the title.
Impact is max(known_titles).
@tarasmadan tarasmadan force-pushed the bug-impact-column branch from 01dbb6e to 8ce37a5 Compare July 8, 2025 12:24
@tarasmadan tarasmadan enabled auto-merge July 8, 2025 16:30
@tarasmadan tarasmadan added this pull request to the merge queue Jul 8, 2025
Merged via the queue into google:master with commit f4e5e15 Jul 8, 2025
18 checks passed
@tarasmadan tarasmadan deleted the bug-impact-column branch July 14, 2025 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants